Category: Geeks r Us
Hi all.
Although I have a multichannel sound card on my computer, JAWS stutters all the time while speaking. Does anyone have any suggestions for fixing this problem?
Which system and which version of jaws, Blake?
I went to the freedomscientific.com site the support page and found the following article. It's really old, and may not apply, but here you go anyway.
Details of Selected Bulletin
Bulletin Type: TSN Number: 40
Date Posted: 10/15/2001
Product Name: JAWS
Version: 3.3
Category: Synthesizer
Short Description:
JAWS stuttering with Eloquence
Problem:
In some cases, when using JAWS with Eloquence with some sound cards, such as the SB Live or the Yamaha Soft Synthesizer, Eloquence sometimes begins to stutter
during intense processing on some computers.
Solution:
There are a couple of things that one might want to check into to see if the stuttering problem can be gotten under control or even totally eliminated.
Check to make sure that the most up-to-date drivers for the particular sound card being used are installed.
Make sure that features such as reverb and sound sampling are turned OFF or set to minimum levels. This can be done by using the properties icon in the
control panel for the specific sound card.
Make sure that no other external applications are installed and running in the system tray. Some sound cards such as the SB Live will install several of
these applications by default, and users are unaware that they are running and taking up processing time from the machine.
Bob,
Thanks for taking the time to search for my problem on Freedom Scientific's technical support site. I implemented all of FS's suggestions, but the problem still exists.
I am using windows XP Professional with Jaws 7.1. My sound card is a PCI Audio 8738 from CMedia. The most recent driver I could find and install was released in 2003.
Any more suggestions from anyone?
Sounds like you have a good system and an up-to-date version of jaws.
If you still have the earlier version of jaws on your computer, try running that and see if you still have the problem.
If the earlier version of jaws doesn't studder, then call freedom and ask them why they put out crap <grin>. Seriously, tell them the difference and see if they have run across this problem with version 7.
If, on the other hand, you still have the problem with the earlier version of jaws, then use alt+ctrl+delete to bring up the task manager and see what you have running, chances are you have some computer hog running thus causing your system to studder.
Just a few suggestions.
Bob
Yeah, i think you need to find out if its just generally your computer beeing slow or something thats maybe conflicting with your synth?
My suggestion is that you do what bob did, but instead of just ending lodes of prosesses, end one and then see if it stuters, this way you can find out what it is that is causing the problem and then maybe fs might have an idea about why its happening.
Hth, BEN.
Here's someting else to consider. Sometimes, the sound card, and video card share an interupt. This doesn't ordinarily pose problems, but when you run a program like jaws, which constantly poles the video card, and makes use of the sound card, you get that studdering effect. the system I have right now, which is a laptop with everything onboard, has this problem. You would do well to check on it, and if that's the problem, you just have to grin and bear it.
Thanks all for posting.
Although I haven't found a perfect fix for the stuttering problem, I have come up with a solution.
Eloquence started stuttering after I installed the latest sound driver from CMedia. When I change my synthesizer to the Microsoft Sapi voices, speech stuttering occurs less frequently.
Although I like Eloquence better, at least I don't have to listen to the stuttering effect as much.
Definitely interupt conflicts.
Does sound like an irq problem. Haven't worked one of those in windows/xp, so I'll go do some research and be back.
Looks like you are in trouble, from my reading. See what you think.
"A general description of IRQ sharing in Windows XP
A general description of IRQ sharing in Windows XP
View products that this article applies to.
Table with 3 columns and 3 rows
Article ID
:
314068
Last Review
:
March 29, 2005
Revision
:
2.1
table end
This article was previously published under Q314068
For a Microsoft Windows 2000 version of this article, see
252420.
Note This article is for informational use only. It does not contain any troubleshooting information. If you are searching for troubleshooting information
that is not mentioned in this article, search the Microsoft Knowledge Base again by using keywords that are listed in the following Microsoft Knowledge
Base article:
242450
How to Query the Microsoft Knowledge Base Using Keywords
SUMMARY
This article offers a general description of how interrupt request (IRQ) sharing is managed in Windows XP. The description includes an explanation of why
many of the devices on your computer seem to use the same IRQ and why Windows XP does not include resource rebalancing.
MORE INFORMATION
In Windows, peripheral component interconnect (PCI) devices can share IRQs. In accordance with the Plug and Play capability that is defined by the PCI specification,
adapters are configured by the computer BIOS and are then examined by the operating system and changed if necessary. Typically, PCI devices have IRQs shared
among them, especially on Advanced Configuration and Power Interface (ACPI) computers that have Windows ACPI support enabled.
In Windows XP, Device Manager may list some or all the devices on your ACPI motherboard as using the same IRQ (IRQ 9). (To view the list of resources, click
either Resources by type or Resources by connection on the View menu). No option is available to change the IRQ setting. Windows takes advantage of the
ACPI features of the motherboard, including advanced PCI sharing. The PCI bus uses IRQ 9 for IRQ steering. With this feature, you can add more devices
without IRQ conflicts.
Windows XP cannot rebalance resources in the same way that Microsoft Windows 98 does. After PCI resources are set, they generally cannot be changed. If
you change to an incorrect IRQ setting or I/O range for the bus that a device is on, Windows XP cannot compensate by rebalancing the resource that was
assigned to that bus.
Windows XP does not have this ability because of the more complex hardware schemas that Windows XP is designed to support. Windows 98 does not have to support
IOAPICs, multiple root PCI buses, multiple-processor systems, and other highly complex hardware schemas. When you are dealing with these hardware schemas,
rebalancing becomes risky and therefore is not implemented in Windows XP except for very specific scenarios. However, PCI devices must be able to share
IRQs. Generally, the ability to share IRQs does not prevent any hardware from working.
The Plug and Play operating system settings in the computer BIOS do not generally affect how Windows XP handles the hardware. However, Microsoft recommends
that you set the Plug and Play operating system setting to No or Disabled in the computer BIOS. For information about viewing or modifying the computer
BIOS settings, see the computer documentation, or contact the computer manufacturer.
Manually assigning IRQs to PCI slots in the system BIOS as a troubleshooting method may work on some non-ACPI systems that use a standard PC hardware abstraction
layer (HAL), but these settings are ignored by Plug and Play in Windows if ACPI support is enabled. If you must manually assign IRQ addresses through the
BIOS to a device on an ACPI motherboard, you must reinstall Windows to force the installation to use a Standard PC HAL.
For more information, click the following artic
sorry ran out of space, but you get the point. Microsoft says not to reassign IRQs.
Bob
have you done a spywear scan lately? I know on my parent's pc, they had a lot of it. It made jaw studder like a studdering fool! heheh smiles.